USHIFT-7446: Ansible: add MicroShift 5.0 pod counts - #7187
Conversation
Add the version-specific readiness thresholds needed by the Ansible boot measurement for MicroShift 5.0 source builds. The values match a live 5.0 deployment with six running non-storage pods and nine ready core pods. Signed-off-by: Sebastian Jug <seb@stianj.ug>
openshift-ci-robot
added
the
jira/valid-reference
|
@sjug: This pull request references USHIFT-7446 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "5.0.0" version, but no target version was set. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository YAML (base), Central YAML (inherited) Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
WalkthroughThe version configuration adds MicroShift 5.0 with an expected pod count of 6 and a total pod count of 9. ChangesMicroShift version configuration
Estimated code review effort: 1 (Trivial) | ~2 minutes Mergeability Score: ⚪ Minimal · up to This localized version-map update adds MicroShift 5.0 boot-readiness thresholds, and no actionable merge-blocking risk remains after normal checks and review. Suggested labels: 🚥 Pre-merge checks | ✅ 15✅ Passed checks (15 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
coderabbitai
Bot
added
the
ready-for-human-review
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
|
/lgtm |
openshift-ci-robot
added
the
verified
|
@ggiguash: This PR has been marked as verified by DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ggiguash, sjug The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-ci
Bot
added
the
approved
|
@sjug: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
3 participants
Summary
Add MicroShift 5.0 boot-readiness thresholds to the Ansible version map.
This prevents 5.0 source builds from failing before boot measurement and unblocks follow-up pull-request performance work in USHIFT-7441.
Testing
ansible/vars/microshift_versions.ymlwithansible-inventoryansible-playbook --syntax-check setup-node.ymlansible-lint --profile min vars/microshift_versions.ymlgit diff --checkmainon RHEL 9.8: service active, API ready, node Ready, six running core non-storage pods, and nine Ready core podsIssue
https://issues.redhat.com/browse/USHIFT-7446
Summary by CodeRabbit